Open the Portico Schema site
Portico Developer Guide
EMV Conversation Flow
Special Processing Rules > EMV > EMV Conversation Flow

EMV tags are persisted by Portico and can be edited prior to the transaction being settled. This allows for the conversational nature of interfacing with a chip card using an EMV capable terminal. For example, the following is a general flow of an EMV conversation to complete a CreditSale transaction. For other flows, see the EMV section of the sample SoapUI project that is included in the SDK.

EMV Conversation Flow

1.

 Client interfaces with the EMV terminal and initiates a conversation with the chip card. The result of this conversation includes obtaining credit authorization EMV tags for the request. Portico is not involved in this conversation between the client and the terminal.

2.

Client initiates a Portico CreditSale request with Track 2 and EMV tag data.

An error will be generated if EMV tag data is not accompanied by Track data.

3.

Portico initiates a request with the Heartland authorization system which includes the Tag Length Value (TLV) fields passed in by the client:
  1. Portico receives the response from the Heartland authorization system.
  2. Portico persists the terminal EMV tag data and issuer response tags to the database.
  3. Portico returns the response to the client which includes the tags returned by the issuer.

4.

Client passes the issuer response tags to the EMV chip card/ terminal and receives the result from the chip card/terminal.

5.

If the EMV chip card/terminal accepts the transaction:
  1. Optionally, the client initiates a CreditTxnEdit using the Gateway Transaction ID returned in the Portico response, sending the EMV terminal result tags in the CreditTxnEdit request.
    1. Portico looks up the original transaction and applies the EMV chip card/terminal result tags to the original EMV tag data.

6.

If the EMV chip card/terminal declines:
  1. After receiving online issuer approval, the client initiates a CreditReversal using the Gateway Transaction ID returned in the Portico response, sending the EMV terminal result tags in the CreditReversal request.
    1. Portico initiates a reversal with the Heartland authorization system. The tags in the reversal that Portico sends are the tags sent by the client in the CreditReversal as well as any tags from the original transaction that weren’t included in the CreditReversal.
  2. Before requesting online authorization, the client initiates a ChipCardDecline, sending the EMV terminal result tags in the ChipCardDecline request.